5T and "limiting WIP"

Author: Seraphim | Created: 2016-02-26 21:45 | Last Activity: 2016-03-7 18:25

Original Post

2016-02-26 21:45
Putting a limit on WIP (work-in-process) is a fundamental element of Agile and Lean workflows, such as Scrum and Personal Kanban. It has so many benefits:
- Reduced task switching
- Increased focus
- Fewer backlogs
- Things get done faster
- Helps identify bottlenecks
- Keeps work flowing smoothly
- Etc.

I am noticing that 5T has a similar effect. I am beginning to think one of the big reasons 5T works so well is that 5T is a simple and effective means to limit WIP – and keep WIP limited to the things that are top-of-mind – cutting out everything else (at least temporarily).

Catch-all lists, on the other hand can theoretically keep EVERYTHING in a state of WIP. Every item on the list is a candidate for imminent action, depending on the particulars of the specific system you are following. With AF1 or FVP, I could theoretically have 100 or more tasks and projects going at once.

Reply by nuntym

2016-03-7 16:53
I am using a "catch all" system right now, SFv3, and it is becoming clear to me that my failures before with Mark Forster's other systems was that I was not being strict with the dismissal process and focusing on too many hard tasks and projects at a time. However, these were cured by having a few weeks with a no-list system.

Reply by Mark Forster

2016-03-7 18:04
nuntym:

<< these were cured by having a few weeks with a no-list system. >>

I've found this effect too. Working with no-list systems seems to make one much more mentally disciplined in this regard - even when one is not using the system.

Reply by nuntym

2016-03-7 18:12
Mark Forster: Probably you should make a blog post about the positive effects of having a go with No List systems for a week or so then :)

Reply by Mark Forster

2016-03-7 18:25
nuntym:

Already on my list.